Quick Configuration

Previous Topic | Next Topic | Contents | Index
Administration Guide | Programmer's Guide | Reference Guide

Subtopics

After installing NonStop DOM on your Open Services System (OSS) system, you must configure the setup before running the system.

This topic describes the basic steps needed to configure the NonStop DOM system. For details on these configuration steps, and for instructions on how to maintain your NonStop DOM system configuration after it is set up, refer to the Administration Guide.

The configuration process consists of customizing several system script files. These files are used to set various environment variables and set up and start NonStop DOM. For details on the NonStop DOM system, refer to the topic The Architecture of NonStop DOM.

This topic guides you through a quick configuration to get your NonStop DOM system up and running. After this process, you should be able to run the stack example located in the samples directory of your NonStop DOM installation.

Before you begin the configuration process, navigate to the base directory of your NonStop DOM installation. By default, this directory is /usr/tandem/nsdoms/.

Customizing the env.sh File

If you installed NonStop DOM into a custom file location, as described in Specifying a Custom Installation Location, then you must modify the env.sh file to reflect your customized installation locations. If you used the default installation locations, then you can skip to the next subtopic, Sourcing the env.sh File.

The env.sh script file sets the default environment variables for your NonStop DOM installation. This file is located in the etc/ subdirectory, which is found in the base directory of your NonStop DOM installation.

Environment Variables Set by env.sh

The following table gives a brief description of each environment variable set in the env.sh script. The table also shows the default script settings.

It is important that you carefully read through the env.sh file, making sure that it sets the correct environment variable values. The majority of the environment variables set up references to the NonStop DOM system directories. You can modify any of the above environment variables to customize your NonStop DOM installation. Also, you should comment any lines in this file if you set corresponding environment variables in your .profile file.

Custom Directory Installations

If you installed NonStop DOM in a custom directory, you will have to modify at least three export statements. This is to reflect the custom file locations you specified when you installed NonStop DOM (these would be the file locations you specified with the -s pax option):

In place of the NSD_ROOT value, enter the new OSS path for your NonStop DOM installation.

In place of the NSD_DIR value, enter the new Guardian path for the NonStop DOM Shared Runtime Library (SRL) files using the following format:

/G/volume/subvolume

In place of the NSD_SUBVOL value, enter the Guardian path for the NonStop DOM SRL files using this notation:

$volume.subvolume

Sourcing the env.sh File

Before you configure or run NonStop DOM, you must source the etc/env.sh script file to properly set up the NonStop DOM environment. To do so, issue the following OSS shell commands from your NonStop DOM base directory:

> cd etc
> . env.sh

Automating the NonStop DOM Environment Settings

If you add the env.sh script to your OSS .profile file, the script will be sourced each time you enter the OSS shell. This effectively automates the environment setup for your NonStop DOM system.

Configuring the NonStop DOM EMS Template

The script file config-ems modifies the NonStop DOM EMS files that were installed on your Guardian system. The EMS template must be created and customized before you can log error messages through the NonStop DOM system.

Creating the EMS Template

To set the correct file codes for the NonStop DOM EMS source files, run the config-ems script:

> config-ems

After running the script, follow these steps to customize and build the NonStop DOM EMS template files:

1. In the file $SYSTEM.ZDOMRT20.BLDDICT, modify the text reading <CHANGE_ME> to specify the volume and subvolume location where the zspiddl and zemsddl files reside on the Guardian file system.
2. In the file $SYSTEM.ZDOMRT20.BLDTMPI, modify the text reading <CHANGE_ME> to specify the volume and subvolume location where the template file resides on the Guardian file system.
3. To build the NonStop DOM EMS template, issue the following command at the TACL prompt:

   > OBEY $SYSTEM.ZDOMRT20.OBEYEMS

Note: If you installed NonStop DOM into a custom file location, you must substitute your custom file location for the $SYSTEM.ZDOMRT20 path given in the above instructions.

Customizing the Initialization Script

To initialize the NonStop DOM configuration database, customize and run the initialization script. Use the file default.db , located in the NonStop DOM etc/ subdirectory, as a template for the initialization script.

Note: By default, the configure script sources in the file default.db to initialize the NonStop DOM configuration database. If you create an initialization script using a name other than default.db, you must ensure that the configure script sources the correct file.

To customize the initialization script, modify the two lines in your new file that contain the tag <CHANGE_ME>. These lines are located near the top of the script, as shown by the following script lines:

# Set the hostname in the next line.
set hostname <CHANGE_ME>
 
# Set the base port in the next line. This port number and the next two
# sequential ports will be used allocated for NSDOM 2.0.
set portnumber0 <CHANGE_ME>
set portnumber1 [expr $portnumber0 + 1]
set portnumber2 [expr $portnumber1 + 1]

The <CHANGE_ME> tags refer to the host name and port number specific to your system. You must modify the script by substituting your system-specific host name and port number.

The hostname reflects the name of the host on which the NonStop DOM framework executes. Depending on how you set your system up, you can use either the symbolic name of the host, the actual IP address of the host, or the full symbolic name of the host (for example, k2.area86@your_company.com). If you are having trouble with one type of hostname definition, try one of the other definitions.

The parameter portnumber0 represents the number of the first port available for this specific configuration. By default, the script initializes three ports for the NonStop DOM framework. You must set the value for portnumber0 , which represents the value of the first available port number. The script then increments this port number to get the script values for portnumber1 and portnumber2 . In this case, the script assumes that the available ports are consecutively numbered. If consecutive port numbers are not available, then you must set them individually, as shown in the following example of script:

set portnumber0    5270
set portnumber1    5253
set portnumber2    5134

Note: The combination of the port number and host name must be unique across each of the ZNCA@comm_server, ZNCB@comm_server, and lsd1@ORB entities.

Specifying TCP/IP Host Names

Once you specify a hostname, the script assigns that name to the other system entities in the script. By default, these entities are two Comm Servers, the Location Service Daemon (LSD), the Event Service, and the TCP server.

If you have a host name that resolves to a single IP address, you can enter this name in place of the host name <CHANGE_ME> tag.

If you have a host name that resolves to more than a single IP address, you cannot use this address as the host name. Instead, use either an alias that resolves to a single IP address or use a static numeric IP address for each of the entities contained in the script. The static IP address must be in the format of nnn.nnn.nnn.nnn.

Specifying Port Numbers

After you have specified your system host names, specify a static port number for the two Comm Servers and the Location Service Daemon (LSD). The only consideration here is that the port numbers you specify must not be used by any other processes within the server IP address space.

Replace the portnumber0 <CHANGE_ME> tag with the static port number to be used for these servers.

Configuring Your NonStop DOM System

Configuring Your NonStop DOM System

Before you configure your NonStop DOM system, ensure that the database files NAMINGDB and NSDCFGDB are not present on your system. If present, these files would be located in the NonStop DOM Guardian subvolume of your NonStop DOM system installation. By default, this directory is $SYSTEM.ZDOMSD20.

If you need to purge existing NAMINGDB and NSDCFGDB files, you can run the unconfigure script.

You are now ready to configure your NonStop DOM system. Issue the following command at your OSS shell to execute the configure script:

> configure

Note: By default, the configure script sources in the file default.db to initialize the NonStop DOM configuration database. Before running the configure script, ensure that the script contains the correct name of your customized initialization script.

Running the configure script produces output similar to the following:

> configure
cfgmgt initialization Completed
LSD initialization Completed
Initializing Naming Service.
Creating POA for Naming Contexts.
Initializing Naming Database.
Creating Root Naming Context IOR.
Root Naming Context IOR saved to config database.
Naming Service initialization complete.

You can verify that this step worked by checking for the presence of the newly created NAMINGDB and NSDCFGDB database files in the NonStop DOM framework Guardian subvolume.

Warning: Do not run the configure script again unless you need to recreate and reconfigure the configuration database of your NonStop DOM system.

Customizing the NonStop DOM PATHMON Process

You use the nsdstart script to start and configure the PATHMON processes under which NonStop DOM runs. By default, the configure script starts the following processes:

The default nsdstart script assumes that the CPUs 0 through 3 are available on your system. If you have a different system configuration, you will need to modify the nsdstart script so it reflects your actual set up.

To modify the script, follow these steps:

1. Give write permission to the script file nsdstart.
2. Modify the number of configured CPUs by changing the cpu entries in the script.
3. If you have increased the number of maxservers in the server class CS (the Comm Server), ensure the subsequent entries in the script are sequential in name and that a corresponding entity for each Comm Server exists in the configuration database.

Note: The first letter for NonStop DOM process names is set in the env.sh file with the environment variable $MY_PREFIX. The default setting is Z.

Previous Topic | Next Topic | Contents | Top
Administration Guide | Programmer's Guide | Reference Guide
Bibliography | Glossary | Index

© Tandem, a division of Compaq. All rights reserved. Legal notices.